System Requirements

General Overview

The OPEN DISCOVERY Streaming workflow is a highly scalable solution that should be deployed in a multi-server environment for effective load balancing and optimal system performance. Component services may be installed on a shared resource as indicated within this help topic. Certain components such as SQL server, IPRO Analytics, and Workers should be installed on separate and dedicated resources. Analysis of the amount of data processed and reviewed within your organization should be conducted by your IT Department and/or IT Vendor to help determine initial system requirements as the following recommendations may not meet your specific needs. Storage requirements are a function of the number of firm cases/matters, data processing and velocity. Ongoing monitoring and regular review of system performance metrics, in addition to routine SQL maintenance is highly recommended to ensure and maintain optimal system performance.

Click the following headers to expand each version.

What's New for 2022.11.0

The following system requirement updates have been made for the 2022.11.0 release of OPEN DISCOVERY. To view the complete list of system requirements, expand the version below.

Updates:

For 2022.11.0, certain machine roles have been renamed to simplify the naming convention used in our VM Deployment model. Additionally, some components have been relocated in this process.
- Within 2022.11.0 Minimum and Recommended Hardware Requirements, name changes have been made to the following tables.
  - Administrative Core:
    - The Web Server component has been renamed: IPRO WEB AUTH (IIS, Auth).
    - The Analytics & dtSearch component has been renamed: IA (Analytics, dtSearch).
    - The IPRO Management components have been split into two separate entries, both with the same existing CPU/RAM specs. This change was necessary to allow multiple EAS management machines to be created within an environment.
      
      ECS (QM, Integration, File Mounting, Redis, File Upload)
      
      EAS (QC, Controller, Review Admin)
  - Scalable Processing Pool
    - Processing Workers have been renamed: EW (Processing Worker)
    - Job Manager Agent has been renamed: JMA (Job Manager Agent)

OPEN DISCOVERY 2022.11.0 System Requirements

2022.11.0 Review End User Minimum Requirements

2022.11.0 Minimum and Recommended Hardware Requirements

2022.11.0 Software Prerequisites

2022.11.0 Network Diagram

2022.11.0 Network Ports Requirements

This information in this section applies to the following OPEN DISCOVERY products and versions:

OPEN DISCOVERY 2022.11.0

The following specifications are a general outline for a typical environment that can be deployed in either a physical or virtual environment. Faster processors and larger amounts of physical memory (RAM) are always a benefit. Network connectivity, network traffic, database size, storage speed, and other factors may impact performance.

OPEN DISCOVERY 2022.11.0 uses the following technologies:

Microsoft Windows Server
Microsoft SQL Server 2016 SP2, 2017, or 2019 (Standard or Enterprise). Make sure the latest CUs are installed.
Microsoft IIS Server
Microsoft .NET Core 3.1 or later
Microsoft .NET Framework 4.8 or later
Microsoft Office Standard Edition
IBM Notes

2022.11.0 Review End User Minimum Requirements

The following specifications are a general outline for a typical environment that can be deployed in either a physical or a virtual environment. Faster processors and larger amounts of physical memory (RAM) is always a benefit. Network connectivity, network traffic, database size, storage speed and other factors may affect performance.

CPU 1 Core / 2.4 GHz or higher
RAM 2 GB or higher
OS Microsoft® Windows® 10 or Server 2016
Software .NET Framework 4.8
Browsers: Chrome, Microsoft Edge (Chromium Release 79), Firefox, Safari
Monitor Minimum screen resolution should be set to minimum 1280x1024.

2022.11.0 Minimum and Recommended Hardware Requirements

The following tables illustrate IPRO’s recommended deployment configuration (1-3 Streaming \ 25 users). If you are deploying additional deployment licenses, please contact Support for a hardware consultation call to review additional requirements. This ensures that all components contact the proper resources, and that components will not conflict with each other.

Note: Each item listed under "Server Role" or "IPRO Component" is intended to be a distinct machine. Modifications to this configuration are not recommended.

Please see the footnotes for additional information. For more detailed hardware questions and customization, please contact IPRO Support.

Administrative Core

SERVER ROLE	CPU(MIN)	RAM(MIN)	CPU(RECMD)	RAM(RECMD)	REQUIREMENTS
SQL Server^{1, 2}	8	32	12	32	Microsoft Windows Server 2016 64-bit, Microsoft SQL Server 2016 SP 2, 2017, or 2019 (Standard or Enterprise) Total Combined Disk IOPS: Minimum 2000 / Recommended 3000 Latency: 99.9% below 20ms or less OS – 100 GB Database – 500 GB or higher TempDB – 50 GB or higher Logs – 150 GB or higher
IPRO WEB AUTH^{3, 4} (IIS, Auth)	4	8	6	12	Microsoft Windows Server 2019 64-bit, Microsoft IIS version 7.0, .NET Core 3.1 or later, and .NET Framework 4.8 or later OS – 100 GB
IAS (Analytics, dtSearch)	12	32	12	96	Microsoft Windows Server 2019 64-bit, .NET Core 3.1 or later, and .NET Framework 4.8 or later OS – 100 GB
ECS (QM, Integration, File Mounting, Redis, File Upload)	4	8	4	8	Microsoft Windows Server 2019 64-bit, .NET Core 3.1 or later, and .NET Framework 4.8 or later OS – 100 GB Windows Page File - Manually configure to 2x RAM total
EAS⁵ (QC, Controller, Review Admin)	4	8	4	8	Microsoft Windows Server 2019 64-bit, .NET Core 3.1 or later, and .NET Framework 4.8 or later OS – 100 GB, Microsoft Office 2016 32-bit, Windows Page File - Manually configure to 2x RAM total

Note: Storage/File Server: Processing data shares should be able to deliver at least 1000 IOPS for each streaming worker license. If not using streaming workflow, use the fastest possible storage for Processing data.

Scalable Processing Pool

IPRO COMPONENT	CPU(MIN)	RAM(MIN)	CPU(RECMD)	RAM(RECMD)	REQUIREMENTS
EWK^{5, 6} (Processing Worker)	4	8	6	8	Microsoft Windows Server 2019 64-bit, .NET Core 3.1 or later, and .NET Framework 4.8 or later Microsoft Office 2016 32-bit, IBM Notes 8.5.2 or 9.0.1 FP10 OS – 100 GB
JMA⁹ (Job Manager Agent)	6	12	8	16	Microsoft Windows Server 2019 64-bit, .NET Core 3.1 or later, and .NET Framework 4.8 or later OS – 100 GB

IPRO COMPONENT

CPU(MIN)

RAM(MIN)

CPU(RECMD)

RAM(RECMD)

REQUIREMENTS

EWK^{5, 6}
(Processing Worker)

Microsoft Windows Server 2019 64-bit, .NET Core 3.1 or later, and .NET Framework 4.8 or later

Microsoft Office 2016 32-bit, IBM Notes 8.5.2 or 9.0.1 FP10

OS – 100 GB

JMA⁹
(Job Manager Agent)

Microsoft Windows Server 2019 64-bit, .NET Core 3.1 or later, and .NET Framework 4.8 or later

OS – 100 GB

LIVE EDA Core

Note: For NetGovern server requirements, see Archive Server Requirements and Storage and Index Server Requirements and Storage.

SERVER ROLE	CPU	RAM	REQUIREMENTS
Master and Worker Node	4	8	Microsoft Windows Server 2016 or 2019 64-bit. Pre-Installed on virtual machine (VM). OS - 250 GB - For OS, Applications, Temp and Swap Space. VM is delivered with this volume, thin-provisioned. See the following details for additional Storage Requirements for Archives, Attachments, and Audit files Virtual Machine Requirements VMWare - ESX 5.5 or higher - Vmotion supported - VMFS (RDM not required, but suggested for better performance) Disk caching on disk array - Thin provisioning supported; thick is suggested on Hyper-V - Hyper-V Server 2016 or later - Disk caching on disk array
Index Server¹⁰	8	32	Centos 7.6 or higher OS - 250 on local disk for OS, Applications and Swap space (Must come already thin-provisioned with the VM) Index storage - Adequate attached storage for indexes. Fiber Channel (FC) connection to a SAN is recommended. iSCSI connections are supported, but performance cannot be guaranteed. Virtual Machine Requirements VMWare ESX 5.5 or higher Vmotion supported Thin provisioning supported; thick is suggested VMFS (RDM not required, but suggested for better performance) Disk caching on disk array Hyper-V Hyper-V Server 2012 or later(Hyper-V 2012 R2 recommended) Thin provisioning supported; thick is suggested Disk caching on disk array

SERVER ROLE

CPU

RAM

REQUIREMENTS

Master and Worker Node

Microsoft Windows Server 2016 or 2019 64-bit. Pre-Installed on virtual machine (VM).

OS - 250 GB - For OS, Applications, Temp and Swap Space. VM is delivered with this volume, thin-provisioned.

See the following details for additional Storage Requirements for Archives, Attachments, and Audit files

Virtual Machine Requirements

VMWare

- ESX 5.5 or higher

- Vmotion supported

- VMFS (RDM not required, but suggested for better performance)

Disk caching on disk array

- Thin provisioning supported; thick is suggested on

Hyper-V

- Hyper-V Server 2016 or later

- Disk caching on disk array

Index Server¹⁰

Centos 7.6 or higher

OS - 250 on local disk for OS, Applications and Swap space (Must come already thin-provisioned with the VM)

Index storage - Adequate attached storage for indexes.

Fiber Channel (FC) connection to a SAN is recommended.

iSCSI connections are supported, but performance cannot be guaranteed.

Virtual Machine Requirements

VMWare

ESX 5.5 or higher

Vmotion supported

Thin provisioning supported; thick is suggested

VMFS (RDM not required, but suggested for better performance)

Disk caching on disk array

Hyper-V

Hyper-V Server 2012 or later(Hyper-V 2012 R2 recommended)

Thin provisioning supported; thick is suggested

Disk caching on disk array

Public API Gateway

Product

Prerequisite

Public API Gateway

Ensure you have the ability to run docker containers. You can find more information at the following links:

https://docs.docker.com/get-docker/

https://docs.docker.com/compose/

Note: This requirement is only for users who plan to use IPRO's Public API functionality.

Footnotes:

1 Provision disks and configure OS & SQL Server settings according to SQL Server Best Practices. For additional details about SQL Server data disk performance, see the "Disk Performance" section of this document.

2 SQL Growth Factors - Environments will benefit from a SQL Server with more cores/RAM/faster storage (IOPS). Processing and Review functions can be split with an additional SQL Server (separate Processing SQL Server and Review SQL Server).

3 .Wildcard SSL Certificate is preferred.

4 English (US) Regional Date format should be set as the machine default for this machine. Whenever possible, users should be restricted from changing this format.

⁵Additional EAS machines may be provisioned as needed to provide additional QC, Controller, or Review Admin stations.

6 The number of eCapture Worker machines is based on the licensing purchased. Additional worker machines beyond available licenses are beneficial during Review productions.

7 All workers in the environment must be configured to prevent Remote Desktop printer redirection. The option "Do not allow client printer redirection" policy setting must be enabled. This can be accomplished through the system’s registry or the group policy (GPO) settings for that environment. Additional information to configure printer redirection settings can be found on Microsoft’s website https://technet.microsoft.com/en-us/library. Once changes have been applied, please reboot all workers. English (US) Regional Date format should be set as the machine default for this machine. Whenever possible, users should be restricted from changing this format.

9 For busier environments, additional Job Manager Agents (JMAs) can be provisioned. Additional CPU/RAM may be added to JMAs; settings changes in SQL are required to make use of these increased resources. All JMAs should be configured with the same CPU/RAM total.

¹⁰ A single index is sufficient for deployments of 4,000 users or fewer. For larger deployments, please contact your NetGovern representative for sizing recommendations.

LIVE EDA Storage Requirements

Note: For NetGovern storage requirements, see Archive Server Requirements and Storage and Index Server Requirements and Storage.

Attachments

Adequate local or attached storage for archived attachments is required.
Attachments are stored in their native format, accounting for approximately 80% of the total mailbox size.
Attachments do not change once written, so they can be stored on read/write media or a WORM device.

Audit

Adequate local or attached storage for audit files is required.

Size of audit files requires approximately 15% the amount of archived data (e.g., 1 TB of archives would mean 150 GB of audit files).
Audit files are very small in size. Recommended block size of storage device is 2K.
Audit files track all operation on archive data and need to be updated, so they cannot be written to a WORM device.

Important Considerations for Virtual Machines

The following important considerations for VMs are:

Do not over-schedule CPU resources, as this can significantly degrade performance.
Always assign Workers RAM as static.

Note: Dynamic RAM can be used on other VMs, but total usage on the VM host should be tracked closely.

Important Considerations for SQL Collation

Our OPEN DISCOVERY applications are designed to work with a specific SQL collation "SQL_Latin1_General_CP1_CI_AS", which is the default value for the OS locale "English (United States)". For our clients outside of the US or who have datacenters outside of the US, this default collation may show as "Latin1_General_CI_AS". This difference in collation can result in misinterpretation and/or false conversion of the data written to SQL, with SQL errors that confirm an existing collation conflict.

To avoid a conflict between the SQL collation being used for the OS locale "English (United States)" and the SQL collation being used for our clients outside the US or who have datacenters outside the US, we recommend that all SQL instances hosting our OPEN DISCOVERY databases are built using the OS locale "English (United States)" collation value “SQL_Latin1_General_CP1_CI_AS”.
For more information about SQL collation, see Microsoft's official webpage.

Other Considerations

If you plan to have reviewers connect from outside your private network (intranet, WAN, etc.), it is recommended that you install the IIS server on a separate machine in your DMZ so that you minimize the risk of exposing internal data.
Having Worker VMs in excess of worker licenses can be a benefit in high-throughput environments, especially when producing from Review.

Disk Performance

SQL requires high-performance storage:
- Any cited IOPS requirements indicates a combined total across all MDF, LDF, and TempDB disks when under high simultaneous load (such as heavy diskspd tests).
- Use DAS or SAN for storage, depending on the environment. Target latency should be sub-20ms in the 3-nines category on diskspd tests.
- When possible, use separate LUNs for MDF and LDF. Ideally, TempDB will also be on a separate LUN from these volumes. Minimize other high-demand applications using these same LUNs.
- SSD is preferred over platter media.
- NAS should always be avoided as this typically leads to unacceptable latency (typically 150ms+ at 3-nines) even with high performance disks.
Project/Client/Case data storage is less demanding:
- Processing data shares should be able to deliver at least 1000 IOPS per streaming worker license. If not using streaming workflow, use the fastest possible storage for Processing data.
- Review cases should be located on fast storage for large and/or priority cases, to ensure performance when retrieving images/natives (also see the Eclipse Web server details that follow), performing IPRO Analytics jobs, searching indexed data, or rebuilding indexes. Slower storage may be used for inactive and/or low-priority cases.
Most discrete components do not heavily use local storage and can function acceptably with slower-performing local storage. Components that benefit from faster local storage include:
- IPRO Review (for rendering documents and images, executing large API tasks, and certain reporting operations). The lowest possible disk latency is preferred.
- Processing Workers, in some situations, will use local storage for archive extraction and some processing tasks. This typically occurs only in a fallback scenario. Faster processing data storage will show more performance improvement than faster local disks on Workers.
- IPRO Review Agents occasionally use local disk space, but primarily use the network share where case data is located. Faster case data storage will show more performance improvement than faster local disk on Agents.

Notes on Using a DMZ

If using a DMZ, the following traffic must be allowed to all internal IPRO servers:

SMB (139,445)

SQL (1433) (only needs to reach SQL Server(s) hosting IPRO software)

LDAP (multiple ports)

2022.11.0 Software Prerequisites

The following is the list of software that must be installed on the machine before OPEN DISCOVERY 2022.11.0 products are installed.

Note: OPEN DISCOVERY requires that the SQL Server common language runtime (CLR) integration feature be enabled. For more information, see https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql/introduction-to-sql-server-clr-integration or similar resources on the internet.

Product

Version

Prerequisite

Installer Pro

1.2

Ensure all users have modify access to
C:\ProgramData\IPRO Tech\logs
User running InstallerPro must have Local Windows Administrator (Run as Administrator) rights
Ensure that the following URLs are white-listed to allow InstallerPro to download the needed software:
- https://myipro.iprotech.com
- https://idp.iprotech.com
- https://storage101.ord1.clouddrive.com
- https://download.visualstudio.microsoft.com (Identity server only)

EASE

2022.9.0

SQL Generator

2022.11.0

OPEN DISCOVERY

2022.11.0

Ensure SQL Server is available Ensure IIS is available
Ensure all users have modify access to C:\ProgramData\IPRO Tech\logs
ApplicationServices prerequisite in InstallerPro, which contains:
- ASP .NET Core 3.1 is installed: Hosting Bundle
- Ensure .NET Framework 4.8 is installed: Runtime

IPRO Processing

2022.11.0

Ensure SQL Server is available
Ensure all users have modify access to C:\ProgramData\IPRO Tech\logs
MS Office 2016 32-bit
Lotus Notes
Lotus Notes 9.0.1 FP 10. (if processing Lotus Notes files)
Adobe PDF Reader

Recommended:

ApplicationServices prerequisite in InstallerPro, which contains:
- ASP .NET Core 3.1 is installed: Hosting Bundle
- Ensure .NET Framework 4.8 is installed: Runtime

Additional QC Machines:

Programs required to reprocess naively, example: CAD Software

Other

2022.11.0

IIS Server Roles (Web Server ONLY):

Common HTTP Features:
- Default Documents
- Directory Browsing - Iffy on if this is required
- HTTP Errors
- Static Content
- HTTP Redirection
Health and Diagnostic:
- HTTP Logging
Performance:
- Static Content Compression
- Dynamic Content Compression
  (Important: Highly NOT Recommended)
Security:
- Request Filtering
Application Development:
- .NET Extensibility 3.5
- .NET Extensibility 4.6
- Application initialization
- ASP .Net 3.5
- ASP .Net 4.6CGI
- ISAP Extensions
- ISAPI Filters

IIS Management Tools:

IIS Management Console

Note: For machines that are on–cloud or on–prem, download the URL Rewrite extension from the following link: URL Rewrite: The Official Microsoft IIS Site and install it on the IIS machine. We can start adding this install to IIS machines before upgrade if we want to get ahead of it for our cloud customers.

2022.11.0 Network Diagram

2022.11.0 Network Ports Requirements

The following is a list of the ports that must be open between components/machines to ensure that the OPEN DISCOVERY products work properly.

Authorization

Name	Type	Service Port	Inbound	Outbound	Description/Service
Auth Service *	Service	9800	9800	443	IPRO Authorization Server
Auth Manager	Application			9800	IPRO Authorization Manager
* Allow for configurable ports

Platform

Name	Type	Service Port	Inbound	Outbound	Description/Service
InstallerPro	Application	8089	8089	8089	IPRO Installation package manager
Redis *	Service	6379	6379		In-memory datastore
Platform Web *	Web Service	ADD Web	ADD Web	Redis
Platform Web API *	Web Service	ADD Web	ADD Web	Identity, SQL, Redis
System Events *	Web Service	ADD Web	ADD Web	Identity, SQL
Identity *	Web Service	ADD Web	ADD Web	SQL (Default 1433) Internet 443 (SSO)
Job Manager Agent *	Service	N/A		ADD Service, Redis, Identity, SQL (Default 1433)
* Allow for configurable ports

Admin

Name	Type	Service Port	Inbound	Outbound	Description/Service
ADD Services *	Web Service	Usually 8443 for SSL or 1124 for internal	ADD Web	9800, SQL (Default 1433)	ADD Service Site
ADD Web *	Web Service	Usually 4443 for SSL or 1125 for internal	ADD Web	ADD Service, SQL (Default 1433), 9000	ADD Web Site
File Upload Server	Service	9000	ADD Service		IPRO File Upload Service
* Allow for configurable ports

Review

Name	Type	Service Port	Inbound	Outbound	Description/Service
IPRO Eclipse Service *	Web Service	Usually 443 or 80 for internal	1433, 5100, 51001, 5150, 8080, 8732, 10900, 50000	SQL (Default 1433), 5100, 51001, 5150, 8080, 8732, 10900, 50000	Eclipse Web Site
Eclipse Chart	App Pool	Same as Eclipse Web		Eclipse Web Port	Binds to the same port as Eclipse Web
Admin	Application		8732	SQL (Default 1433), 8080, ADD Service	Eclipse Admin Application
dtSearch Service	Service	5100	5100		dtService Service
Content Analyst	Service	8080	8080	SQL (Default 1433)	Content Analyst (CAAT)
IPRO Analytics	Service	10900	10900, 50000	SQL (Default 1433) 10900,50000	IPRO Analytics Service
* Allow for configurable ports

Processing

Name	Type	Service Port	Inbound	Outbound	Description/Service
Controller*	Application		51001, 5150, 5160, 1433, 9800	ADD Service, 9800, 1433, Identity	eCapture Controller
Queue Manager	Application		ADD Service, 1433	ADD Service, SQL (Default 1433), Identity	eCapture Queue Manager
Integration Service	Service	5150, 5160, 51001	ADD Service,1433, 5150, 5160, 51001	ADD Service, SQL (Default 1433), Identity	IPRO Integration Service
File Mounting Service	Service	51205		ADD Service, Identity	File Mounting Service
Worker	Application			ADD Service, SQL (Default 1433), Identity	eCapture Worker Application
QC	Application			ADD Service, SQL (Default 1433), Identity	eCapture QC Application
Relativity (Optional)	Service	40100	40100		IPRO Relativity Service

Configuring Ports in the Firewall

Note: Configuring ports is generally outside scope of support and must be set up by the client.

OPEN DISCOVERY 2022.10.0 System Requirements

2022.10.0 Review End User Minimum Requirements

2022.10.0 Minimum and Recommended Hardware Requirements

2022.10.0 Software Prerequisites

2022.10.0 Network Diagram

2022.10.0 Network Ports Requirements

This information in this section applies to the following OPEN DISCOVERY products and versions:

OPEN DISCOVERY 2022.10.0

OPEN DISCOVERY 2022.10.0 uses the following technologies:

Microsoft Windows Server
Microsoft SQL Server 2016 SP2, 2017, or 2019 (Standard or Enterprise). Make sure the latest CUs are installed.
Microsoft IIS Server
Microsoft .NET Core 2.2.1
Microsoft .NET Core 3.1.2
Microsoft Office Standard Edition
IBM Notes

2022.10.0 Review End User Minimum Requirements

CPU 1 Core / 2.4 GHz or higher
RAM 2 GB or higher
OS Microsoft® Windows® 10 or Server 2016
Software .NET Framework 4.8
Browsers: Chrome, Microsoft Edge (Chromium Release 79), Firefox, Safari
Monitor Minimum screen resolution should be set to minimum 1280x1024.

2022.10.0 Minimum and Recommended Hardware Requirements

Note: Each item listed under "Server Role" or "IPRO Component" is intended to be a distinct machine. Modifications to this configuration are not recommended.

Please see the footnotes for additional information. For more detailed hardware questions and customization, please contact IPRO Support.